Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Polkadot v0.9.43 #69

Merged
merged 16 commits into from
Nov 16, 2023
Merged

Polkadot v0.9.43 #69

merged 16 commits into from
Nov 16, 2023

Conversation

cdamian
Copy link
Contributor

@cdamian cdamian commented Oct 13, 2023

Adding support for polkadot-v0.9.43.

@cdamian
Copy link
Contributor Author

cdamian commented Oct 13, 2023

cc @mustermeiszer rebased this branch on latest master to ensure that we get the latest changes in here as well.

Copy link
Contributor

@lemunozm lemunozm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for working on this! 🙌🏻

Comment on lines 279 to 286
.map_err(|e| {
tracing::error!(
target: DEFAULT_COLLATOR_LOG_TARGET,
error = ?e,
"Could not cast upward messages.",
)
})
.ok()?;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm asking here, but the question goes more for all these patterns. If fudge intention is to be used for testing. Why, instead of tracing and propagating a None, do we no just unwrap everywhere? That way, when it doesn't work, the error just panic with the correct message in the correct line which generate it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe @mustermeiszer can provide a better answer to this ^^.

In my fudge branch for xcm tests I'm addressing some of these and propagating some more errors in cases similar to this.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You might not want to use it soley for testing. You can also use it for other things like forking a network, etc. I think unwrapping in a dependency library is not really an option IMO.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unwrapping in a dependency library is not really an option IMO.

Ok, this makes sense 👍🏻

Copy link
Collaborator

@mustermeiszer mustermeiszer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks already good.

@cdamian cdamian mentioned this pull request Oct 20, 2023
@cdamian
Copy link
Contributor Author

cdamian commented Oct 25, 2023

Latest changes currently being tested here as well. Keeping this PR as a drat until we confirm that tests work as expected and no other changes are needed.

Copy link
Collaborator

@mustermeiszer mustermeiszer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sick, sick, sick!

Nice that you got that one working!

Comment on lines +439 to +446
let call = PRuntimeCall::System(frame_system::Call::remark_with_event {
remark: remark.clone(),
});

let instruction: Instruction<PRuntimeCall> = Transact {
origin_kind: OriginKind::SovereignAccount,
require_weight_at_most: Weight::from_parts(200_000_000, 0),
call: call.encode().into(),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SICK!

@mustermeiszer mustermeiszer marked this pull request as ready for review November 13, 2023 12:59
@cdamian
Copy link
Contributor Author

cdamian commented Nov 15, 2023

@mustermeiszer can we go ahead and merge this and keep the branch?

@cdamian cdamian merged commit eeb2dab into master Nov 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants